Skip to content

Update EIP-7928: change BAL retention period to WSP#10940

Merged
eth-bot merged 2 commits intoethereum:masterfrom
nerolation:linter-fixes2
Dec 16, 2025
Merged

Update EIP-7928: change BAL retention period to WSP#10940
eth-bot merged 2 commits intoethereum:masterfrom
nerolation:linter-fixes2

Conversation

@nerolation
Copy link
Copy Markdown
Contributor

@nerolation nerolation commented Dec 16, 2025

As based on the discussion here, EL may store enough BAL to enable nodes that were offline for less than the WSP to catch up doing re-execution (for which BALs are needed):
https://discord.com/channels/595666850260713488/1364000387195076608/1450572627700617268

@nerolation nerolation requested a review from eth-bot as a code owner December 16, 2025 23:17
@github-actions github-actions bot added c-update Modifies an existing proposal s-draft This EIP is a Draft t-core labels Dec 16, 2025
@eth-bot
Copy link
Copy Markdown
Collaborator

eth-bot commented Dec 16, 2025

✅ All reviewers have approved.

@eth-bot eth-bot enabled auto-merge (squash) December 16, 2025 23:18
eth-bot
eth-bot previously approved these changes Dec 16, 2025
Copy link
Copy Markdown
Collaborator

@eth-bot eth-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All Reviewers Have Approved; Performing Automatic Merge...

auto-merge was automatically disabled December 16, 2025 23:21

Head branch was pushed to by a user without write access

@eth-bot eth-bot enabled auto-merge (squash) December 16, 2025 23:22
Copy link
Copy Markdown
Collaborator

@eth-bot eth-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All Reviewers Have Approved; Performing Automatic Merge...

@nerolation nerolation changed the title Update EIP-7928: fix linter issues Update EIP-7928: change BAL retention period to WSP Dec 16, 2025
@eth-bot eth-bot merged commit f7efd2a into ethereum:master Dec 16, 2025
16 of 18 checks passed
Copy link
Copy Markdown

@trizist trizist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This proposal is a strong and well-motivated step toward scalable execution-layer performance. Block-Level Access Lists strike a pragmatic balance between full witnesses and transaction-level access lists by providing deterministic, post-execution state information with manageable overhead. The ability to enable parallel disk reads, parallel transaction execution, executionless state updates, and faster state root computation makes BALs particularly compelling as Ethereum moves toward multi-core clients and more execution-light validation models.

The recent change to retain BALs for the weak subjectivity period is especially important, as it aligns BAL availability with Ethereum’s security assumptions and improves robustness for long-offline nodes. While client complexity and storage considerations are real trade-offs, the measured size overhead appears reasonable given the substantial gains in sync performance, validation efficiency, and future compatibility with Verkle trees and statelessness research. Overall, this EIP meaningfully advances Ethereum’s long-term execution roadmap without altering EVM semantics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c-update Modifies an existing proposal s-draft This EIP is a Draft t-core

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants